Low-Power WUS Rel-18

 RAN1#110-bis-e

9.13   Study on low-power wake-up signal and receiver for NR

Please refer to RP-222644 for detailed scope of the SI on low power WUS and receiver for NR.

R1-2208667         Work plan for low-power wake up signal and receiver for NR  vivo

[110bis-e-R18-LP_WUS-03] – Xiaodong (vivo)

TR skeleton endorsement by October 12

R1-2208666         TR 38.869 skeleton for study on low-power wake up signal and receiver for NR vivo

R1-2210430        TR 38.869 skeleton for study on low-power wake up signal and receiver for NR               vivo

Decision: As per email decision posted on Oct 13th, the TR skeleton is endorsed as version 0.0.1 as basis for future updates.

9.13.1     Evaluation on low power WUS

Including evaluation methodology, performance results, and performance comparison with Rel-15/16/17 UE power saving mechanisms.

R1-2209075        Discussion on evaluations on LP WUS       Intel Corporation

Proposal 1: For idle/inactive mode

• For the deeper sleep mode of main radio, the power consumption, additional transition energy and transition time can be respectively assumed as 0.015, 2000 and 400ms for the evaluation of power saving and latency reduction.
• The power consumption for the active or inactive state of LP-WUR is assumed to 100uW – 1mW and 1-10uW for the evaluation of power saving and latency reduction
• Performance metrics include ratio of power consumption reduction, latency reduction
• In the modeling, LP-WUS is assumed to replace PEI PDCCH
• Study LP-WUS to provide more information than PEI PDCCH

Proposal 2: For connected mode

• Two modes can be considered for evaluations
• Model 1: LP-WUS detection in DRX ON for XR operation having periodic traffic with jitter in packet arrival time
• Model 2: LP-WUS to trigger active PDCCH monitoring or SSSG switching assuming aperiodic traffic, e.g., ftp traffic is configured to the UE
• Performance metrics include ratio of power consumption reduction, latency reduction
• LP-WUS may provide a function that is similar to DCI format 2_6
• Monitoring LP-WUS is further extended in the DRX ON time.

Proposal 3:

• Two performance metrics, false alarm rate of 1% and mis detection rate of 0.1% can be used in LP-WUS evaluation.
• If LP-WUS consists two parts, the link performance of the two parts need to be jointly considered to derive the final performance metrics
• The sensitivity for LP-WUS can be derived by the required SINR for LP-WUS detection

Proposal 4: Adopt Table 4 as a start point for the detailed link-level simulation assumptions for LP-WUS detection.

Decision: The document is noted.

R1-2209502        Evaluation on low power WUS     MediaTek Inc.

·        Proposal 1            Use cases can at least include wearables and XR for LP WUR/S.

·        Proposal 2            KPI can includes power consumption, data latency, coverage (MIL), and robustness (MDR and FAR) for LP WUR/S.

·        Proposal 3            For UE power and latency evaluation, introduce a power consumption model for LP-WUR, including WUR on/off power states and transition time/energy.

·        Proposal 4            For UE power and latency evaluation, introduce a new power state of "power off" for the Rel-15 reference UE and Rel-17 RedCap UE.

·        Proposal 5            For UE power and latency evaluation, reuse the traffic model in TR 38.875 as the baseline.

·        Proposal 6            For coverage evaluation, at least consider carrier frequencies of 700MHz and 2.6GHz.

·        Proposal 7            For coverage evaluation, reuse a template in R1-2009293 for Rel-18 RedCap.

·        Proposal 8            For coverage evaluation, LP WUR/WUS link-level simulation (LLS) is essential to evaluate the required SNR and the occupied LP-WUS bandwidth.

·        Proposal 9            For LP WUR/WUS LLS evaluation, consider a general baseband model including interference, low-pass filter, and frequency error.

·        Proposal 10          L1 signal and procedure design for LP WUR/WUS should consider coexistence and overhead impact.

Decision: The document is noted.

R1-2208378         Evaluation of Low Power WUS and initial performance results               FUTUREWEI

R1-2208417         Evaluation methodology for LP-WUS           Huawei, HiSilicon

R1-2208572         Discussion on evaluation on low power WUS             Spreadtrum Communications

R1-2208668         Evaluation methodologies for R18 LP-WUS/WUR    vivo

R1-2208686         Discussion on evaluation on LP-WUS           InterDigital, Inc.

R1-2208698         Low power WUS Evaluation Methodology  Nokia, Nokia Shanghai Bell

R1-2208843         Evaluation discussion on lower power wake-up signal              OPPO

R1-2208960         Deployment scenarios and evaluation methodologies for low-power WUS               CATT

R1-2209199         Evaluation on LP-WUS     ZTE, Sanechips

R1-2209270         Evaluation on low power WUS       xiaomi

R1-2209361         Discussion on evaluation methodology and applicable scenarios for low power WUR               CMCC

R1-2209605         On performance evaluation for low power wake-up signal        Apple

R1-2209621         Discussion on low power WUS evaluation   Rakuten Symphony

R1-2209665         Discussion on the evaluation methodology for low power WUS             Lenovo

R1-2209685         Discussion on evaluation for low power WUS             Sharp

R1-2209756         Evaluation on LP-WUS/WUR         Samsung

R1-2209766         Initial view on evaluation of low-power WUS             Rakuten Mobile, Inc

R1-2209862         Evaluation framework for low power WUS  Ericsson

R1-2210010         Evaluation methodology for LP-WUS           Qualcomm Incorporated

R1-2210051         Discussion on Evaluation on Low power WUS           EURECOM

R1-2210169         Discussion on evaluation methodology for low power WUS     NTT DOCOMO, INC.

R1-2210197         On LP-WUS evaluation    Nordic Semiconductor ASA

R1-2210222         Evaluation for low power WUS       Sony

[110bis-e-R18-LP_WUS-01] – Xiaodong (TBD)

Email discussion on evaluation of LP WUS by October 19

-        Check points: October 14, October 19

R1-2210437        FL summary#1 of evaluation on low power WUS   Moderator (vivo)

From Oct 12th GTW session

For future meetings on LP WUS:

Use the following terminology for future discussion,

·        Main radio (MR): the Tx/Rx module operating for legacy NR signals/channels apart from signals/channel related to low-power wake-up.

·        LP-WUR (LR): The Rx module operating for receiving/processing signals/channel related to low-power wake-up.

Agreement

For evaluation, 1 Rx chain for LP-WUS receiver is baseline.

Agreement

Both RRC IDLE/INACTIVE and CONNECTED modes are to be studied as part of the LP-WUS/WUR SI.

·        FFS: Further prioritization if needed during the study item.

Agreement

Take the following power model for main radio for evaluation in LP-WUS/WUR SI,

·        For IoT and wearable cases, reuse TR38.875 power model as baseline.

·        For eMBB and other cases, reuse TR38.840 power model as baseline.

·        Introduce ‘Ultra-deep sleep’ power state for main radio of UEs with LP-WUS receiver and reusing power model option 1 value of ‘Ultra-deep sleep’for LPHAP evaluation, i.e.,

o   FFS: The details of ‘Ultra-deep sleep’ power state

R1-2210512        FL summary#2 of evaluation on low power WUS   Moderator (vivo)

From Oct 18th GTW session

Agreement

·        The following power models are used ‘Ultra-deep sleep’ power state for main radio for evaluation

Note1:

·        Ramp-up time may consist of the procedure for [main radio hardware tune on e.g., boot, memory load and etc.]

·        Time for sync/re-sync consists of the procedure for [main radio to re-synchronization with the serving gNB etc.]

o   FFS: X and whether/how to have different values depending on other factors, e.g., signal-to-noise ratio.

o   Companies can report the assumption of X in the initial evaluation.

·        Ramp up and down energy includes power for ramp-up and ramp-down. Energy consumption for sync/re-sync is separately calculated.

·        The total time for main radio transition from ultra-deep sleep to active/micro sleep state is the sum of ramp-up time and time for sync/re-sync.

o   FFS whether/how to define ramp-down time, whether to separately describe the ramp-down energy consumption.

Note 2: the power state transitions in this table refer to transitions between ultra deep sleep state and active / micro sleep state.

Note 3: The values inside of ‘[ ]’ are to be used as starting point of future study on LP-WUS.

Agreement

The following power model for LP-WUR/WUS evaluation is considered,

·        Relative power unit for LP-WUR ‘off’ state, i.e., the LP-WUR does not perform monitoring:

o   [0.001]

·        Relative power unit for LP-WUR ‘on’ state, i.e., the LP-WUR performs monitoring:

o   [0.005/0.01/0.02/0.03/0.05/0.1/0.2/0.5/1/2/4]

o   Other values are not precluded to be evaluated

o   FFS: Mapping from values to a LP-WUR architecture or LP-WUR mode of operation

·        No additional transition energy and transition time between ‘on’ and ‘off’ state as start point, FFS any transition energy and transition time if needed.

Note1: A unit of power is defined to be the same for main receiver and LP-WUS receiver.

Note2: the values provided is for the purpose of studying power saving gain, and the values can be further revisit and categorization depending on the receiver architecture discussion.

Note3: For LP-WUR ‘on’ state, more than one values within the above range may be used for evaluation (e.g. for a single LP-WUR architecture)

FFS: LP-WUR power consumption values for FR2.

Decision: As per email decision posted on Oct 19th,

Agreement

For R18 LP-WUS/WUR power evaluation in RRC connected mode, the following can be considered,

• XR traffic model with evaluation methodologies and assumptions captured in TR 38.838.
• eMBB traffic model with evaluation methodologies and assumptions captured in TR 38.840
• Heartbeat traffic models in 3GPP TR 38.875.
• Other models are not precluded.

Company to further provide the followings,

• Parameters (e.g., frame rate, data rate, jitter range, DRX configurations and etc if needed.)
• How to use LP-WUS, e.g., LP-WUS to trigger/adapt PDCCH monitoring
• Other details if any

Agreement

• For LP-WUS coverage evaluation, the noise figure of LP-WUR is
• Options : [9, 12, 15, 18, 21, 24], Other values can be reported by companies
• FFS: how to determine the NF option.
• The values provided is for the purpose of studying coverage of LP-WUS, and it can be further revisited depending on the receiver architecture discussion.

Agreement

For the performance evaluations of LP-WUS candidate designs, it is assumed that

• The miss-detection rate (MDR) of LP-WUS [1%],
• The false-alarm rate (FAR) of LP-WUS
• [0.1%, 1%, 10%]
• Other values are not precluded for studying reported by companies
• Note: if LP-WUS for wake-up indication consists of two parts or even multiple parts, the proposed MDR/FAR should take into account the reception performance of the two or more parts jointly
• The above values applied in both RRC CONNECTED and IDLE/INACTIVE mode.
• FFS FAR requirement based on the study outcome of the impact of FAR on power consumption / power saving gain / system overhead
• FFS: Note: FAR should be evaluated both in the absence of gNB transmissions and in the presence of transmissions from gNB. Proponent to provide the details.

Decision: As per email decision posted on Oct 20th,

Agreement

For system impact analysis, the following performance metrics are considered to be provided,

For power and latency evaluation of the LP-WUS, the following performance metrics are considered to be provided.

Companies to report baseline scheme, e.g., PO monitoring with i-DRX, e-DRX, with or without PEI

Companies to report the power consumption / power saving gain considering the FAR impact , latency considering MDR impact

Other performance metrics (e.g., mobility) can be reported by companies (if any)

Agreement

The following is assumed for RRC IDLE/INACTIVE evaluation,

Agreement

For evaluation of the coverage of LP-WUS, the methodology and assumptions in R17 CovEnh SI (described in TR38.830) is reused as baseline.

• MIL is used as the metric for LP-WUS coverage evaluation
• urban (2.6GHz/4GHz), rural(700MHz) scenario for FR1 are considered to be evaluated, others (e.g., FR2) are not precluded.

Note: For IoT/wearables devices, refer to R17 Redcap SI TR38.875 if the assumptions differ from TR38.830.

Companies report any other assumptions which differ from the TR38.875/ TR38.830, e.g., Tx and Rx loss

Companies are encouraged to compare LP-WUS with at least PDCCH for paging, PUSCH, others are not precluded. FFS: Target coverage of LP-WUS

Final summary in R1-2210668.

9.13.2     Low power WUS receiver architectures

R1-2208418        On architectures of LP-WUS receiver       Huawei, HiSilicon

·        Receive architectures with the following design aspects are studied for LP-WUR:

o   Use low quality LNA (the price is higher noise figure);

o   Use lower accuracy LO without PLL, for example, ring-type LO;

o   Avoid high-resolution and high sampling rate quantizer;

o   Avoid complicated baseband processing.

·        The LP-WUS needs to have a suitable design to permit simplified receiver architectures.

·        RAN1 to study:

o   Evaluating the power consumption of potential LP-WUR architectures to build the power model for calculating the power saving gain;

o   Determining the link and system level assumption for receiving LP-WUS based on the implementation of potential LP-WUR receivers, including:

§  Maximum time and frequency error;

§  Bit-width and sampling rate of ADC for digital baseband processing

o   Evaluating the coverage of LP-WUS based on the noise figure of potential LP-WUR receivers.

·        OOK, FSK can be potential LP-WUS candidate modulation schemes for low power wake-up signal modulation.

·        Study receivers (a) with a single down-conversion operation, and (b) without LO as potential LP-WUR architectures.

Decision: The document is noted.

R1-2210011        Receiver architecture for LP-WUS             Qualcomm Incorporated

·        Proposal 1: 3GPP shall not mandate the implementation of certain receiver architecture.

·        Proposal 2: 3GPP RAN1 determines the design target of LP-WUR for WAN application.

Decision: The document is noted.

R1-2208379         Low Power WUS Receiver Architectures Considerations and Modeling               FUTUREWEI

R1-2208481         Low Power WUS receiver architecture          TCL Communication Ltd.

R1-2208573         Discussion on low power WUS receiver architectures Spreadtrum Communications

R1-2208669         Discussion on low power wake-up receiver architecture           vivo

R1-2208687         Discussion on LP-WUS receiver architectures            InterDigital, Inc.

R1-2208699         Low Power WUS receiver architectures        Nokia, Nokia Shanghai Bell

R1-2208844         Discussion on low power WUS receiver       OPPO

R1-2208961         Design consideration of Low-Power WUS receiver    CATT

R1-2209076         Discussion on LP-WUS receiver architecture              Intel Corporation

R1-2209200         LP-WUS receiver architectures       ZTE, Sanechips

R1-2209503         Low power WUS receiver architectures        MediaTek Inc.

R1-2209606         On low power wake-up receiver architectures             Apple

R1-2209622         Receiver architectures for low power WUS  Rakuten Symphony

R1-2209634         Discussion on Low power WUS receiver architectures              Panasonic

R1-2209666         Discussion on the receiver architecture for low power WUS     Lenovo

R1-2209757         Receiver architecture for LP-WUS  Samsung

R1-2209863         Low power WUS receiver architectures        Ericsson

R1-2210052         Discussion on Low power WUS receiver architectures              EURECOM

R1-2210198         On LP-WUS architecture  Nordic Semiconductor ASA

R1-2210223         On LP-WUS receiver architectures Sony

[110bis-e-R18-LP_WUS-02] – Sigen (Apple)

Email discussion on LP WUS receiver architecture by October 19

-        Check points: October 14, October 19

R1-2210479        Summary #1 on [110bis-e-R18-LP_WUS-02] LP WUR architecture Moderator (Apple)

From Oct 14th GTW session

Conclusion

RAN1 does not intend to mandate the implementation of any specific type(s) of LP WUR architecture at the UE.

·        Note: this does not prevent RAN4 from defining requirements for LP WUR in the normative phase.

Agreement:

Study at least the following three types of receiver architectures for LP-WUR:

•        Architecture with RF envelope detection

•        Heterodyne architecture with IF envelope detection

•        Homodyne/zero-IF architecture with baseband envelope detection

•        Note: The details of each type of receiver architecture are discussed separately.

•        Note: Above receiver architectures are considered suitable for OOK modulation. Some of the architectures can be applicable for other modulations such as FSK.

R1-2210480         Summary #2 on [110bis-e-R18-LP_WUS-02] LP WUR architecture      Moderator (Apple)

Decision: As per email decision posted on Oct 20th,

Agreement

Study the architecture with RF envelope detection based on at least the following diagram for LP-WUR.

• The RF signal is converted into baseband signal directly via an RF envelope detector.
• There is no Local Oscillator (LO) and no Phase-Locked Loop (PLL).
• 1-bit or multi-bit ADC is applied.
• Some component(s), e.g., RF LNA and/or BB AMP, can be optionally applied.
• High-Q matching network and/or RF BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers.
• FFS the support of band and/or carrier tuning

Agreement

Study the heterodyne architecture with IF envelope detection based on at least the following diagram for LP-WUR.

• The RF signal is down converted into IF signal via an RF mixer with a LO. The IF signal is converted into baseband signal via an IF envelope detection.
• There may be one or multiple IF stages depending on design.
• The choice of the LO is one of the major factors that determines the power consumption.
• Lower power consumption can be achieved by relaxing the accuracy and stability requirements of the LO. However, such increased frequency offset and phase noise should be taken into account in the design and evaluation.
• FLL (frequency locked loop) may replace PLL for non-coherent detection.
• 1-bit or multi-bit ADC is applied.
• High-Q matching network and/or RF BPF and/or IF BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers.
• Some component(s), e.g., RF LNA and/or IF AMP and/or BB AMP, can be optionally applied.
• Image rejection filter or an image rejection mixer is required.
• FFS the support of band and/or carrier tuning
• FFS the choice of IF frequency range

Agreement

Study the homodyne/zero-IF architecture with baseband envelope detection based on at least the following diagram for LP-WUR.

• The RF signal is directly down converted into baseband signal via an RF mixer with a LO.
• Baseband envelope detection can be done either in analog domain or in digital domain depending on design, which is not explicitly shown in the diagram.
• The choice of the LO is one of the major factors that determines the power consumption.
• Lower power consumption can be achieved by relaxing the accuracy and stability requirements of the LO. However, such increased frequency offset and phase noise should be taken into account in the design and evaluation.
• FLL (frequency locked loop) may replace PLL for non-coherent detection.
• 1-bit or multi-bit ADC is applied.
• High-Q matching network and/or RF BPF and/or BB BPF [and/or BB LPF] can be used to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers.
• No image rejection filter is required.
• Some component(s), e.g., RF LNA and/or BB AMP, can be optionally applied.
• FFS the support of band and/or carrier tuning

Agreement

Further study the receiver architectures for FSK, with two examples shown below:

• Example 1: parallel OOK receivers and a comparator circuit, e.g.,

• Each path can be implemented using either of [the architecture with RF envelope detection,] heterodyne architecture with IF envelope detection, or homodyne/zero-IF architecture with baseband envelope detection.
• Example 2: using an FM-to-AM detector [or an FM detector]
• Alt 1: Use an analog FM-to-AM detector with a similar architecture as for OOK (e.g. heterodyne or zero-IF architecture), except that the envelope detector is replaced by a FM-to-AM detector.
• Analog FM-to-AM detector can be implemented at least in BB or low-IF.

• Alt 2: Use a FM-to-AM detector [or an FM detector] implemented in digital domain after ADC, with a heterodyne or zero-IF architecture.
• Digital FM-to-AM detector implementation can be considered as part of digital baseband processing.
• Here is an example of using zero-IF architecture:
• The FM-AM detector can be implemented using a frequency discriminator, which converts frequency variations into amplitude changes. It can be implemented in either analog domain (as in Alt 1) or digital domain (as in Alt 2).
• One example, as shown in the figure below, is a conventional quadrature FM discriminator. It multiplies received frequency modulated signal with a phase shifted version, followed by a low pass filter. The amplitude of the output signal is proportional to the frequency of the input signal.

• Note: Other architectures are not precluded.

Agreement

For the analysis of a receiver architecture, companies are encouraged to provide at least the following (when applicable):

• Details of the receiver
• Receiver architecture type
• Assumed modulation/waveform/coding
• Presence of a RF LNA / IF AMP / BB AMP, and the corresponding gain, if any
• Local oscillator
• Type of oscillator and the corresponding frequency accuracy/drifting
• Handling of time/frequency impairments
• Presence of PLL or FLL
• ADC: sampling rate, bit-width
• Assumed signal bandwidth and guard band, and frequency location within a carrier (including whether it is fixed or can be flexible)
• RF/IF/BB filter characteristics (e.g. type of filter, order, cut-off frequency/frequencies), if any
• Baseband processing (e.g., sequence correlation detection / decoding, other signal processing, if any)
• Assumed frequency band(s) and the support of band and/or carrier tuning
• Duty cycle handling of WUS and other signals (if any)
• Interference rejection capability (including both adjacent-channel interference and interference from adjacent subcarriers occupied by legacy NR signals or other LP WUS)
• Handling of inter-cell interference
• Whether there is any mobility support function, e.g. measurement capability
• Performance metrics
• Power consumption during active monitoring/reception and during off state (and breakdown if possible)
• Noise figure
• Sensitivity/coverage
• Data rate
• FFS: other performance metrics for, e.g., cost/complexity, interference rejection capability and inter-cell interference handling
• Note: The performance and design of receiver architecture is expected to be dependent on WUS design. This list can be updated later when the discussion on WUS signal/procedure design (AI 9.13.3) starts.

Final summary in R1-2210666.

9.13.33     L1 signal design and procedure for low power WUS

Including any higher layer protocol changes relevant to RAN1. For RAN1#110bis-e, tdocs are to be submitted only for information. There will not be online discussions in RAN1#110bis-e.

R1-2208380         Low Power WUS Design  FUTUREWEI

R1-2208419         Signal design and procedure for LP-WUS     Huawei, HiSilicon

R1-2208482         L1 signal design and procedure for low power WUS  TCL Communication Ltd.

R1-2208574         Discussion on L1 signal design and procedure for low power WUS        Spreadtrum Communications

R1-2208670         Discussion on physical signal and procedure for low power WUS          vivo

R1-2208688         Discussion on L1 signal design and procedure for LP-WUS     InterDigital, Inc.

R1-2208700         L1 signal design and procedure for low power WUS  Nokia, Nokia Shanghai Bell

R1-2208845         L1 signal design consideration on lower power wake-up signal OPPO

R1-2208962         Physical layer signals and procedures for Low-Power WUS     CATT

R1-2209077         Discussions on L1 signal design and procedure for low power WUS      Intel Corporation

R1-2209158         Discussion on L1 signal design and procedure for LP-WUS     NEC

R1-2209201         LP-WUS design and related procedure          ZTE, Sanechips

R1-2209271         Discussions on L1 signal design and procedure for low power WUS      xiaomi

R1-2209362         Discussion on L1 signal design for low power WUS   CMCC

R1-2209504         L1 signal design and procedure for low power WUS  MediaTek Inc.

R1-2209607         On the L1 signal design and procedures for low power wake-up signal  Apple

R1-2209635         Discussion on low power wake up signal design         Panasonic

R1-2209667         Discussion on the L1 signal design and procedure for low power WUS  Lenovo

R1-2209686         L1 signal design and procedure for low power WUS  Sharp

R1-2210238         Signal design and procedure for LP-WUS     Samsung              (rev of R1-2209758)

R1-2209864         L1 signal design and procedure for low power WUS  Ericsson

R1-2210012         L1 signal design and procedures for LP-WUR             Qualcomm Incorporated

R1-2210054         Discussion on L1 signal design and procedure for low power WUS        EURECOM

R1-2210171         Discussion on L1 signal design and procedure for low power WUS        NTT DOCOMO, INC.

R1-2210199         On LP-WUS signal design Nordic Semiconductor ASA

R1-2210224         LP-WUS L1 signal design and procedures    Sony

 RAN1#111

9.13   Study on low-power wake-up signal and receiver for NR

Please refer to RP-222644 for detailed scope of the SI on low power WUS and receiver for NR.

[111-R18-LP_WUS] – Xiaodong (vivo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.13.1     Evaluation on low power WUS

Including evaluation methodology, performance results, and performance comparison with Rel-15/16/17 UE power saving mechanisms.

R1-2210850         Evaluation of Low Power WUS and Performance Results        FUTUREWEI

R1-2210908         Evaluations for LP-WUS  Huawei, HiSilicon

R1-2211030         Evaluation methodologies for R18 LP-WUS/WUR    vivo

R1-2211182         Remaining issues of Deployment scenarios and evaluation methodologies for low-power wakeup receiver     CATT

R1-2211252         Discussion on evaluation on low power WUS             Spreadtrum Communications

R1-2211269         Low power WUS Evaluation Methodology  Nokia, Nokia Shanghai Bell

R1-2211319         Discussion on evaluation on LP-WUS           InterDigital, Inc.

R1-2211325         Power requirement for WUS            Everactive

R1-2211348         Evaluation on low power WUS       xiaomi

R1-2211420         Discussion on evaluations on LP WUS          Intel Corporation

R1-2211471         Evaluation for lower power wake-up signal  OPPO

R1-2211628         Evaluation of low power WUS        Sony

R1-2211834         On performance evaluation for low power wake-up signal        Apple

R1-2211907         Evaluation on LP-WUS     ZTE, Sanechips

R1-2212006         Discussion on evaluation methodology for low power WUS     NTT DOCOMO, INC.

R1-2212070         Evaluation on LP-WUS/WUR         Samsung

R1-2212142         Evaluation methodology for LP-WUS           Qualcomm Incorporated

R1-2212158         Evaluation framework for low power WUS  Ericsson

R1-2212261         Evaluation on low power WUS       MediaTek Inc.

R1-2212316         Evaluation of low power WUS        Rakuten Symphony

R1-2212384         Discussion on Evaluation on Low power WUS           EURECOM

R1-2212410         Discussion on the evaluation for low power WUS       Lenovo

R1-2212417         On LP-WUS evaluation    Nordic Semiconductor ASA

R1-2212768        FL summary#1 of evaluation on low power WUS   Moderator (vivo)

Presented in Nov15th session.

R1-2212899        FL summary#2 of evaluation on low power WUS   Moderator (vivo)

From Nov 17th session

Update the agreement in RAN1#110bis-E as follows,

For system impact analysis, the following performance metrics are considered to be provided,

For power and latency evaluation of the LP-WUS, the following performance metrics definitions provided for future study

Companies to report baseline scheme, e.g., PO monitoring with i-DRX, e-DRX, with or without PEI

Companies to report the power consumption / power saving gain considering the FAR impact, latency considering MDR impact

Other performance metrics (e.g., mobility) can be reported by companies (if any)

Agreement

Update the IDLE/INACTIVE state traffic model option 1 as follows and remove traffic model option 2,

·        The traffic arrival is modeled as a Poisson Arrival Process where inter-arrival times are exponentially distributed, the mean arrival time is P = Y_REF / R_{E, REF}, where

o   R_{E, REF}= 1%, 0.1%, 0.01% or 0.001% and Y_REF = 1.28s

o   Per group paging probability R_G = 1 – (1 – R_E)^N, where N is the number of UEs in the group

§  FFS: Value of N

·        For LP-WUS

o   Both per group and UE paging can be assumed.

Note：

·        For i-DRX with i-DRX cycle duration Y second,

o   Per UE paging probability R_E = 1 – (1 – R_{E, REF} )^Y/Y_REF

o   Per group paging probability R_G = 1 – (1 – R_E)^N, where N is the number of UEs in the group

·        For e-DRX with K i-DRX cycles duration, L PTW duration of L i-DRX cycles, and an i-DRX cycle duration Y second

o   Per UE paging probability is

§  R_E = 1 – (1 – R_{E, REF} )^(K-L)Y/Y_REF for the first i-DRX cycle within the PTW

§  R_E = 1 – (1 – R_{E, REF} )^LY/Y_REF for each of the remaining L-1 i-DRX cycles within the PTW

o   Per group paging probability R_G = 1 – (1 – R_E)^N, where N is the number of UEs in the group

o   L=4 (as agreed in RAN1#110bis)

Agreement

For MR, at least for FR1 evaluation,

·        Number of SSBs for sync/re-sync for MR is up to 10

o   Companies to report timeline and energy consumption

·        Companies to provide feasibility analysis for transition time and transition energy with aim to converge to one or two set of values in RAN1#112

Agreement

The following power model for LP-WUR is used for evaluation for FR1,

FFS: whether further categorization/sub-categorization is needed and how.

Final summary in R1-2213005.

9.13.2     Low power WUS receiver architectures

R1-2210909         Discussion on architecture of LP-WUS receiver          Huawei, HiSilicon

R1-2211031         Discussion on low power wake-up receiver architecture           vivo

R1-2211067         Low Power WUS receiver architecture          TCL Communication Ltd.

R1-2211183         Low-Power WUS receiver Architectures and its performance  CATT

R1-2211253         Discussion on low power WUS receiver architectures Spreadtrum Communications, H3C

R1-2211270         Low Power WUS Receiver Architectures     Nokia, Nokia Shanghai Bell

R1-2211320         Discussion on LP-WUS receiver architectures            InterDigital, Inc.

R1-2211326         FSK Architectures for WUR            Everactive

R1-2211421         Discussion on LP-WUS receiver architecture              Intel Corporation

R1-2211472         Discussion on low power WUS receiver       OPPO

R1-2211599         Discussion on low power wake up receiver architectures          Panasonic

R1-2211835         On low power wake-up receiver architectures             Apple

R1-2211908         LP-WUS receiver architectures       ZTE, Sanechips

R1-2212007         Discussion on low power WUS receiver architectures NTT DOCOMO, INC.

R1-2212071         Receiver architecture for LP-WUS  Samsung

R1-2212143         Receiver architecture for LP-WUS  Qualcomm Incorporated

R1-2212159         Low power WUS receiver architectures        Ericsson

R1-2212262         Low power WUS receiver architectures        MediaTek Inc.

R1-2212317         Receiver architectures for low power WUS  Rakuten Symphony

R1-2212411         Design consideration of Low-Power WUS receiver    Lenovo

R1-2212418         On LP-WUS architecture  Nordic Semiconductor ASA

R1-2212674        Summary #1 on LP WUR architecture      Moderator (Apple)

Presented in Nov15th session.

R1-2212675        Summary #2 on LP WUR architecture      Moderator (Apple)

From Nov 17th session

Agreement

Include the following in the LS to RAN4:

RAN1 kindly asks RAN4 to take RAN1 agreements into account, study at least the LP WUR architectures that RAN1 identifies and provide feedback, potentially considering the aspects including but not limited to:

• The reasonable assumption on adjacent channel selectivity (ACS) assumption for the study and the impact on the LP WUR architectures and signal design
• The impact of adjacent subcarrier interference suppression/rejection on the LP WUR architectures if LP WUS is multiplexed with other signals/channels in frequency, including e.g.
• The necessity of guard band (if needed, the minimum guard band) between LP WUS subcarriers and adjacent subcarriers
• Whether it is feasible to have LP WUS location flexible within the carrier
• The feasible noise figure(s) for each type of LP WUR architectures
• Impact, if any, LP-WUS transmission on existing gNB emissions/compliance requirements
• The potential RF impairments to be considered include e.g. timing error, frequency error, image impact, LO leakage (DC offset) and flicker (1/f) noise
• Whether certain LP WUR architectures can support multi-band capability
• Note: RAN1 may or may not identify further architecture(s) for the study.

Include all agreements on 9.13.2. Mention that other agreements have been made in other AIs.

R1-2212953        Draft LS to RAN4 on low-power wake-up receiver architectures     Moderator (Apple)

Decision: As per decision on Nov 18th, the draft LS is endorsed. Final LS is approved in R1-2212999.

Agreement

The following observation to be captured in TR38.869:

For the architecture with RF envelope detection,

• It can achieve relatively low power consumption due to the removal of LO/PLL.
• Interference suppression for adjacent channel interference requires very high-Q matching network and/or RF BPF, which is challenging due to the high Q values and may require off-chip components.
• Interference suppression for interference from legacy NR signals and/or other LP WUS on adjacent subcarriers, if performed in RF, requires very high-Q matching network and/or RF BPF, which is challenging due to the high Q values and may require off-chip components.
• The support of multiple bands and/or carriers may require multiple high-Q matching networks and/or RF BPFs or multiple off-chip components.
• RF LNA can be applied to improve sensitivity, with the cost of additional power consumption.
• The noise figure can be relatively high.

Agreement

The following observation to be captured in TR38.869:

For homodyne/zero-IF architecture with baseband envelope detection,

• For the support of band and/or carrier tuning, the band and/or carrier tuning can be achieved via tuning the LO frequency.
• The matching network and RF BPF for LP WUR may or may not reuse those of the main radio.
• It is more effective and less complex to use BB BPF/LPF instead of high-Q matching network and/or RF BPF to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers.
• Using FLL instead of PLL consumes less power, but it may result in larger frequency error.
• It can suffer from LO leakage (DC offset) and flicker (1/f) noise. The impact may be alleviated by using BB BPF in some cases.
• RF LNA can be applied to improve sensitivity, with the cost of additional power consumption.
• The baseband envelope detection can be done in either analog domain (before ADC) or digital domain (after ADC).

Agreement

The following observation to be captured in TR38.869:

For heterodyne architecture with IF envelope detection,

• For the support of band and/or carrier tuning, the band and/or carrier tuning can be achieved via tuning the LO frequency.
• The matching network and RF BPF for LP WUR may or may not reuse those of the main radio.
• It is more effective and less complex to use IF BPF instead of high-Q matching network and/or RF BPF to suppress adjacent channel interference or interference from legacy NR signals and/or other LP WUS on adjacent subcarriers.
• Using FLL instead of PLL consumes less power, but it may result in larger frequency error.
• The IF frequency can be properly selected to avoid LO leakage (DC offset) and flicker (1/f) noise.
• Image rejection can be done via either image rejection filter or image rejection mixer.
• Image rejection filter can be done in either RF or IF, which may require high-Q filter.
• Image rejection mixer requires two-branch (I/Q) mixing with good matching in gain and phase, which consumes additional power.
• RF LNA and/or IF AMP can be applied to improve sensitivity, with the cost of additional power consumption.

Final summary in R1-2212676.

9.13.33     L1 signal design and procedure for low power WUS

Including any higher layer protocol changes relevant to RAN1.

R1-2210851         Low Power WUS Design  FUTUREWEI

R1-2210910         Signal design and procedure for LP-WUS     Huawei, HiSilicon

R1-2211032         Discussion on physical signal and procedure for low power WUS          vivo

R1-2211068         L1 signal design and procedure for low power WUS  TCL Communication Ltd.

R1-2211184         Physical layer signals and procedures for Low-Power WUS     CATT

R1-2211271         L1 signal design and procedures for low power WUS Nokia, Nokia Shanghai Bell

R1-2211321         Discussion on L1 signal design and procedure for LP-WUS     InterDigital, Inc.

R1-2211327         L1 WUS Considerations   Everactive

R1-2211349         Discussions on L1 signal design and procedure for low power WUS      xiaomi

R1-2211422         Discussions on L1 signal design and procedure for low power WUS      Intel Corporation

R1-2211473         L1 signal design consideration on lower power wake-up signal OPPO

R1-2211546         Discussion on L1 signal design and procedure for low power WUS        Spreadtrum Communications

R1-2211600         Discussion on low power wake up signal design         Panasonic

R1-2211629         L1 signal design and procedure for LP-WUS Sony

R1-2211704         Discussion on L1 signal design and procedure for LP-WUS     CMCC

R1-2211836         On the L1 signal design and procedures for low power wake-up signal  Apple

R1-2211857         L1 signal design and procedure for low power WUS  Sharp

R1-2211909         LP-WUS design and related procedure          ZTE, Sanechips

R1-2212008         Discussion on L1 signal design and procedure for low power WUS        NTT DOCOMO, INC.

R1-2212072         Signal design and procedure for LP-WUS     Samsung

R1-2212144         L1 signal design and procedures for LP-WUR             Qualcomm Incorporated

R1-2212160         L1 signal design and procedure for low power WUS  Ericsson

R1-2212263         L1 signal design and procedure for low power WUS  MediaTek Inc.

R1-2212318         L1 signal design for low power WUS            Rakuten Symphony

R1-2212366         Discussion on L1 signal design and procedure for LP-WUS     NEC

R1-2212385         Discussion on L1 signal design and procedure for low power WUS        EURECOM

R1-2212412         Discussion on the L1 signal design and procedure for low power WUS  Lenovo

R1-2212419         On LP-WUS signal design Nordic Semiconductor ASA

R1-2212749        Summary #1 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From Nov 15th session

Study the following as candidates for LP-WUS

·        multi-carrier (MC)-ASK/[OOK] waveform

·        multi-carrier (MC)-FSK waveforms

·        reusing existing OFDMA-based signals/channels

Agreement

·        Study generation and link performance of multi-carrier (MC)-ASK (including OOK) waveform

o   Study techniques to generate waveform by modulating sub-carriers of CP-OFDM [FFS : drop CP at transmitter)] symbol, consider up to M bits transmitted per OFDM symbol, where M is FFS.

§  Note that above does not preclude DFT-S-OFDMA

·        Study generation and link performance of multi-carrier (MC)-FSK waveforms

o   Study techniques to generate waveform by modulating sub-carriers of CP-OFDM symbol [FFS : drop CP at transmitter)] symbol, consider up to M bits transmitted per OFDM symbol, where M is FFS.

·        Study link performance of OFDMA-based signals/channels considering at least the existing signal/channel structure (e.g. CSI-RS, SSS)

o   Other signal/channel structures are not precluded

·        For next meeting, companies to provide input on aspects to consider that might impact link performance

R1-2212866        Summary #2 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From Nov 17th session

Agreement

For the purpose of study, the BW of one LP-WUS is not greater than X (FFS X is 5 or 20) MHz for FR1, study further

• whether BW of LP-WUS is configurable (implicitly or explicitly)
• size of guard band [FFS: within or outside of BW X], if any
• whether there is different X for Idle, Connected, Inactive modes

FFS: Whether FR2 is included in the scope of LP-WUS SI

Agreement

For a UE support LP-WUR in IDLE/INACTIVE mode,

• Study how to reduce UE power consumption due to existing RRM measurement requirements at least for mobility support,
• study feasibility of RRM measurements performed by LP-WUR, at least for serving/camping cell, based on signals detected by LP-WUR
• FFS: measurement metric
• FFS: whether and how to identify cell/ tracking area
• FFS: need for neighbouring cells
• FFS: need for relaxation of existing RRM measurement requirements (for UE)

Final summary in R1-2212978.

 RAN1#112

9.13   Study on low-power wake-up signal and receiver for NR

Please refer to RP-222644 for detailed scope of the SI on low power WUS and receiver for NR.

[112-R18-LP_WUS] – Xiaodong (vivo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2300486         TR 38.869 v010: Study on low-power wake up signal and receiver for NR               Rapporteur (vivo)

From Friday session

[Post-RAN1#112-LP_WUS1] Email discussion on revised TR approval by March 7 – Xiaodong (vivo)

9.13.1     Evaluation on low power WUS

Including evaluation methodology, performance results, and performance comparison with Rel-15/16/17 UE power saving mechanisms.

R1-2300052         Evaluation of Low Power WUS and performance results          FUTUREWEI

R1-2300100         Evaluations for LP-WUS  Huawei, HiSilicon

R1-2300241         Discussion on evaluation on low power WUS             Spreadtrum Communications

R1-2300273         Evaluation for lower power wake-up signal  OPPO

R1-2300375         Evaluation on LP-WUS     ZTE, Sanechips

R1-2301799         Evaluation methodologies and results  for R18 LP-WUS/WUR              vivo       (rev of R1-2300476)

R1-2300559         Evaluation on low power WUS       xiaomi

R1-2300597         Discussion on evaluation on LP-WUS           InterDigital, Inc.

R1-2300664         Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR              CATT

R1-2300698         Low power WUS Evaluation Methodology  Nokia, Nokia Shanghai Bell

R1-2300892         Evaluation of low power WUS        Sony

R1-2300969         Evaluations on LP-WUS   Intel Corporation

R1-2301112         Discussion on evaluation for LP-WUS          LG Electronics

R1-2301194         On LP-WUS evaluation    Nordic Semiconductor ASA

R1-2301289         Evaluation on LP-WUS/WUR         Samsung

R1-2301371         On performance evaluation for low power wake-up signal        Apple

R1-2301438         Evaluation methodology for LP-WUS           Qualcomm Incorporated

R1-2301516         Discussion on evaluation methodology for low power WUS     NTT DOCOMO, INC.

R1-2301558         Low power WUS evaluations          Ericsson

R1-2301577         Evaluation on low power WUS       MediaTek Inc.

R1-2302006        FL summary#1 of evaluation on low power WUS   Moderator (vivo)

Presented in Tuesday session

R1-2302140        FL summary#2 of evaluation on low power WUS   Moderator (vivo)

Presented in Thursday session

R1-2302212        FL summary#3 of evaluation on low power WUS   Moderator (vivo)

From Friday session

Conclusion:

The FAR definition does NOT include the impact of the falsely alarmed for wake-up due to the detection of a LP-WUS which is intended to wake-up/alarm the LP-WUR of another UE within the same UE group.

Agreement

The following characteristics for target use cases are considered in the study item:

• IoT cases including e.g., industrial wireless sensors, controllers, actuators and etc, including the following characteristics,
• FFS: latency
• primary for small form devices
• power-sensitive
• static, nomadic or limited mobility
• Wearable cases including e.g., smart watches, rings, eHealth related devices, and medical monitoring devices etc.,
• FFS: latency
• primary for small form devices,
• power-sensitive
• low/medium speed, FFS: high speed
• eMBB cases including e.g., XR/smart glasses, smart phones and etc.,
• FFS: latency
• devices form is various and not restricted
• power-sensitive
• low/medium speed, FFS: high speed

Note: other use cases/characteristics are not precluded if any.

Agreement

For evaluation, at least for FR1 MR ultra-deep sleep state, (Ramp-up and down transition energy, ramp-up time) is as follows,

·        Alt 1: (15000, 400ms)

·        Alt 2: ([40000], [800ms])

Company to report which alternative they use for which use cases.

Agreement

For coverage evaluation, the following is used,

Note: The descriptions above does not change the agreements for coverage in the RAN1#110-bis.

[Post-RAN1#112-LP_WUS2] Email discussion on remaining evaluation methodology details. For email approval by March 9 – Xiaodong (vivo)

• R1-2302212: [H] Proposals 1A-1-v7, Proposal 1A-3-v6
• R1-2302213 (from 9.13.3): High-FL6-Proposal-5

9.13.2     Low power WUS receiver architectures

R1-2300053         Low Power WUS Receiver Architectures, Considerations, and Modeling               FUTUREWEI

R1-2300101         Discussion on architecture of LP-WUS receiver          Huawei, HiSilicon

R1-2300242         Discussion on low power WUS receiver architectures Spreadtrum Communications

R1-2300274         Discussion on low power WUS receiver       OPPO

R1-2300362         Discussion on low power wake up receiver architectures          Panasonic

R1-2300376         LP-WUS receiver architectures       ZTE, Sanechips

R1-2300477         Discussion on low power wake-up receiver architecture           vivo

R1-2300598         Discussion on LP-WUS receiver architectures            InterDigital, Inc.

R1-2300665         Low-Power WUS receiver Architectures and its performance  CATT

R1-2300699         Low Power WUS Receiver Architectures     Nokia, Nokia Shanghai Bell

R1-2300970         Discussion on LP-WUS receiver architecture              Intel Corporation

R1-2301195         On LP-WUS architecture  Nordic Semiconductor ASA

R1-2301290         Receiver architecture for LP-WUS  Samsung

R1-2301372         On low power wake-up receiver architectures             Apple

R1-2301439         Receiver architecture for LP-WUS  Qualcomm Incorporated

R1-2301517         Discussion on low power WUS receiver architectures NTT DOCOMO, INC.

R1-2301559         Low power WUS receiver architectures        Ericsson

R1-2301578         Low power WUS receiver architectures        MediaTek Inc.

R1-2301816        Summary #1 on LP WUR architecture      Moderator (Apple)

From Tuesday session

Agreement

Study the parallel receiver architectures (as examples that can be captured in the TR) for FSK based on the following diagrams:

• Parallel homodyne architecture receiver

• The observations made for homodyne/zero-IF architecture with baseband envelope detection in RAN1#110b/111 are also applicable here.
• Parallel heterodyne architecture receiver

• The observations made for heterodyne architecture with IF envelope detection in RAN1#110b/111 are also applicable here.
• Note: Other architectures are not precluded.
• The OOK receiver architectures agreed for study in RAN1#110bis-e are also examples that can be captured in the TR

Agreement

Study the receiver architectures (as examples that can be captured in the TR) for FSK with frequency to amplitude conversion based on the following diagrams:

• Homodyne architecture receiver with frequency to amplitude conversion
• I/Q branches are required for frequency to amplitude conversion in digital BB.

• Heterodyne architecture receiver with frequency to amplitude conversion

• Companies provide the exact type FFS what type(s) of frequency to amplitude conversion being is studied.
• Note: Other architectures are not precluded.

R1-2301817        Summary #2 on LP WUR architecture      Moderator (Apple)

From Thursday session

Agreement

For OFDMA-based signals/channels, study the receiver architectures based on the following diagrams:

• I/Q branches are required for digital BB processing.
• Digital BB processing may or may not include FFT (companies to provide details on how).
• For sequence-based OFDM signals/channels, digital BB processing includes sequence correlation in either time domain (without FFT) or frequency domain (after FFT).
• Proponent companies should at least provide details on power consumption reduction compared to the MR regarding the RF and digital BB processing.
• Companies are encouraged to provide the break-down for the components.
• The potential power reduction compared to the main radio may come from e.g.:
• Lower performance LNA/amplifier
• Oscillator/PLL with relaxed performance requirements
• ADC with lower sampling rate and smaller bit-width
• Reduced BB processing complexity compared to the MR
• Companies are encouraged to provide the performance analysis corresponding to the considered power consumption considering the impact of e.g. phase noise, I/Q mismatch.
• Companies to report whether the LP WUR is assumed to share components with MR. In case of component sharing, the potential impact on the MR ultra-deep sleep state should be considered.
• Companies to report the possible number of information bits
• In addition, companies should consider the power consumption in the OFF state and the transition energy.

Agreement

For the study on LP WUR architecture, power consumption relative to the deep sleep state of the MR is provided.

·        Deep sleep state of non-RedCap UE should be assumed

Final summary in R1-2301818.

9.13.33     L1 signal design and procedure for low power WUS

Including any higher layer protocol changes relevant to RAN1.

R1-2300054         Low Power WUS Design  FUTUREWEI

R1-2300102         Signal design and procedure for LP-WUS     Huawei, HiSilicon

R1-2300169         L1 signal design and procedure for low power WUS  TCL Communication Ltd.

R1-2300243         Discussion on L1 signal design and procedure for low power WUS        Spreadtrum Communications

R1-2300275         Design consideration on lower power wake-up signal and procedure      OPPO

R1-2301862         Discussion on low power wake up signal design         Panasonic            (rev of R1-2300363)

R1-2300377         LP-WUS design and related procedure          ZTE, Sanechips

R1-2300478         Discussion on physical signal and procedure for low power WUS          vivo

R1-2300560         Discussions on L1 signal design and procedure for low power WUS      xiaomi

R1-2300599         Discussion on L1 signal design and procedure for LP-WUS     InterDigital, Inc.

R1-2300666         Physical layer signals/procedures and higher layer protocol for Low-Power WUR               CATT

R1-2300700         L1 signal design and procedures for low power WUS Nokia, Nokia Shanghai Bell

R1-2300727         Discussion on signal design and procedure for LP-WUS           China Telecom

R1-2300795         L1 signal design and procedure for low-power WUS  Sharp

R1-2300819         Discussion on L1 signal design and procedure for LP-WUS     NEC

R1-2300893         L1 signal design and procedures for LP-WUS             Sony

R1-2300971         Discussions on L1 signal design and procedure for LP-WUS    Intel Corporation

R1-2301026         Discussion on L1 signal design and procedure for LP-WUS     CMCC

R1-2301113         Discussion on L1 signal design and procedure for LP-WUS     LG Electronics

R1-2301133         Discussion on L1 signal design and procedure for low power WUS        EURECOM

R1-2301196         On LP-WUS signal design Nordic Semiconductor ASA

R1-2301291         Signal design and procedure for LP-WUS     Samsung

R1-2301373         On the L1 signal design and procedures for low power wake-up signal  Apple

R1-2301440         L1 signal design and procedures for LP-WUR             Qualcomm Incorporated

R1-2301518         Discussion on L1 signal design and procedure for low power WUS        NTT DOCOMO, INC.

R1-2301560         L1 signal design and procedure for low power WUS  Ericsson

R1-2301579         L1 signal design and procedure for low power WUS  MediaTek Inc.

R1-2301638         Discussion on the L1 signal design and procedure for low power WUS  Lenovo

R1-2302003        Summary of discussions on L1 signal design and procedure for low power WUS               Moderator (Nordic Semiconductor ASA)

From Tuesday session

Agreement (modified as shown below in red during Thursday session)

For MC-ASK waveform generation, where K is size of iFFT of CP-OFDMA, N is number of SCs used by LP-WUS including potential guard-bands, study further

• Option OOK-1: Single-bit in 1 OFDM symbol, SCs of LP-WUS are

• OOK=1 means all SCs are modulated
• OOK=0 means all SCs are zero power (from base-band point of view)

• Option OOK-2: Parallel M-bit OOK in frequency domain,
• N SCs of LP-WUS is further separated into M segments (M=2 in Figure) possibly with guard-bands in-between and/or around
• OOK=1 means all SCs in segment are modulated
• OOK=0 means all SCs in segment are zero power (from base-band point of view)
• FFS architecture.

• Option OOK-3: Multi-tone single-bit OOK
• N SCs of LP-WUS is separated into L segments (L=2 on Figure) without guard-bands in-between segment, but possibly around
• OOK=1 means 1 sub-carrier (known by UE) of each segment is modulated, rest of SC is zero power (from base-band point of view)
• OOK=0 means all SCs in all segments are zero power (from base-band point of view)
• FFS architecture

• Option OOK-4: Transform M-bit OOK in time domain
• N SCs of OOK-1 are generated by a transformation (DFT/Least square)
• N’ samples are generated from M-bits
• signal modification may or may NOT be used
• truncation or other additional modification may or may NOT be used, if not used, N is the same as N’
• N’ can be the same as K

• FFS modulated SCs are e.g. QAM symbols, sequences or other signals
• Companies to report their assumptions
• potential guard-band SCs are zero power (from base-band point of view)
• [optionally, 2 additional segments, one always modulated and one always zero power (from base-band point of view) can be transmitted]
• Other options are not precluded (e.g. OOK-1 with multiple bits in one OFDM symbol)

Agreement

Study synchronisation signal used by LP-WUR, if needed, based on

• Option 1: aperiodic signal transmitted as part of LP-WUS
• FFS: Whether the signal can additionally be transmitted separately from LP-WUS
• Option 2: periodic signal transmitted separately from LP-WUS
• Option 3: Option1 + Option2

R1-2302158        Summary#2  of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From Thursday session

Agreement

For M-bit MC-FSK generation study further the following options

• Option FSK-1: N SCs of LP-WUS are separated to M pairs of segments with potential guard-bands in-between and around.
• segment comprises one sub-carrier or multiple contiguous SCs
• in a pair of segments one segment is modulated, other segment is zero power (from base-band point of view)
• Option FSK-2: N SCs of LP-WUS are separated to 2^M segments with potential guard-bands in-between and around.
• segment comprises one sub-carrier or multiple contiguous SCs
• one segment from 2^M segments is modulated, other segments of SCs are zero power (from base-band point of view)
• M >0
• N >1

·        Study how to generate segment in time domain, e.g. OOK-1 or OOK-4

·        Other options are not precluded.

Agreement

For MC-ASK or MC-FSK waveform generation, SCS of a CP-OFDM symbol used for LP-WUS generation can be the same as SCS used for other NR transmissions in CP-OFDM symbol overlapping in time with, study whether SCS can be different, also study

• FDM/TDM multiplexing with other NR transmissions
• link performance
• impact to legacy UEs
• impact on gNB

Agreement

Study further pros and cons of the following monitoring behaviors of LP-WUR

·        Option1: Duty cycle, corresponds to LP-WUR switches between ON/OFF states

·        Option2: Continuous monitoring, corresponds to LP-WUR is ON all the time

R1-2302213        Summary#3  of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From Friday session

Agreement

Study potential measurement metric used for RRM measurements performed by LP-WUR.

·        examples of measurement metric are signal quality, signal power, detection rate of LP-WUS/synch signal

·        companies to report assumption of signal used for measurements

 RAN1#112-bis-e

9.11   Study on low-power wake-up signal and receiver for NR

Please refer to RP-222644 for detailed scope of the SI on low power WUS and receiver for NR.

9.11.1     Evaluation on low power WUS

Including evaluation methodology, performance results, and performance comparison with Rel-15/16/17 UE power saving mechanisms.

R1-2302331         Evaluation of LP-WUS and Performance Results       FUTUREWEI

R1-2302339         Evaluations for LP-WUS  Huawei, HiSilicon

R1-2303897         Evaluation methodologies for R18 LP-WUS/WUR    vivo       (rev of R1-2302506)

R1-2302570         Evaluation for lower power wake-up signal  OPPO

R1-2302621         Discussion on evaluation on low power WUS             Spreadtrum Communications

R1-2302687         Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR              CATT

R1-2302815         Evaluations on LP-WUS   Intel Corporation

R1-2302827         Discussion on evaluation on LP-WUS           InterDigital, Inc.

R1-2302861         Evaluation of low power WUS        Sony

R1-2302890         Low power WUS Evaluation Methodology   Nokia, Nokia Shanghai Bell

R1-2302948         Evaluation on LP-WUS     ZTE, Sanechips

R1-2302968         Evaluation on low power WUS       xiaomi

R1-2303150         Evaluation on LP-WUS/WUR         Samsung

R1-2304057         Evaluation on low power WUS       MediaTek Inc.     (rev of R1-2303332)

R1-2303429         Discussion on evaluation for LP-WUS          LG Electronics

R1-2303505         On performance evaluation for low power wake-up signal        Apple

R1-2303537         On LP-WUS evaluation    Nordic Semiconductor ASA

R1-2303612         Evaluation methodology for LP-WUS           Qualcomm Incorporated

R1-2303759         Low power WUS evaluations          Ericsson

[112bis-e-R18-LP_WUS-01] – Xiaodong (vivo)

Email discussion on evaluation of LP WUS by April 26th

-        Check points: April 21, April 26

R1-2304076        FL summary #1 of evaluation methodologies on LP-WUS/WUR      Moderator (vivo)

Presented in April 20th GTW session

Decision: As per email decision posted on April 26th,

Agreement

Update as followings for the e-DRX paging probability

Note:

• For i-DRX with cycle duration Y second,
• Per UE paging probability R_E = 1 – (1 – R_{E, REF} )^Y/Y_REF
• For e-DRX with K i-DRX cycles duration, PTW duration of L i-DRX cycles, and an i-DRX cycle duration Y second
• Per UE paging probability is
• R_E = 1 – (1 – R_{E, REF} )^(K-L+1)Y/Y_REF for the first i-DRX cycle within the PTW
• R_E = 1 – (1 – R_{E, REF} )^Y/Y_REF for each of the remaining L-1 i-DRX cycles within the PTW
• L=4

Agreement

Update the additional transition energy from [T_{LR, ramp-up} *(P_ON+P_OFF)/2] to [T_{LR, ramp-up} *(P_ON-P_OFF)/2] for LP-WUR power model.

·        Note: this assumes the power consumption during the transition time is sum of additional transition energy and LP-WUR OFF energy, e.g., similar definition as the additional transition energy in TR38.840

Working Assumption

For Model 1 of frequency error, Frequency displacement (Fd), defined as the difference between ideal frequency and frequency due to 1) clock drifting (ΔF); and 2) residual frequency error from previous synchronization/calibration (Fr), is given as Fd (ppm)=ΔF (ppm) +Fr(ppm),

·        Companies to report Fr and important assumptions for achieving Fr, e.g., if MR can assist to calibrate LP-WUR to correct the frequency error or if LP-WUR can only correct the frequency error based on LP-WUS synchronization signal.

R1-2304150        FL summary #2 of evaluation methodologies on LP-WUS/WUR      Moderator (vivo)

From April 26th GTW session

Agreement

The period of synchronization signal that LP-WUR used for at least power evaluation can be

• Existing SSB periodicity can be used from gNB transmission perspective for evaluations assuming SSB, companies to report how often used for LP-WUR
• For evaluations assuming LP-SS
• {320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms}
• Companies to report other important assumptions if any, e.g., durations of LP-SS to achieve enough T/F accuracy
• Other values are not precluded

Note: companies to report the purpose of the synchronization signal along with evaluations, e.g. can be for LR synchronization (i.e., time and/or frequency tracking) and/or measurement.

Working Assumption

For evaluation purpose, FAR target is determined across a reference time duration T of one or multiple LP-WUS attempts/trials,

• UE have N attempts within T, 
• Company to report (FAR target, T, N)
• For example,
• if UE makes a single decision based on multiple correlations for a sequence in the monitor occasion, these correlations are considered as UE implementation in ONE trial/attempt.
• if UE performs decoding in a monitor occasion, a single decoding is considered as ONE trial/attempt.
• If UE performs N non-overlap attempts within the reference time duration, the false alarm event for the attempts are assumed as independent.

Companies to provide the assumed side conditions to attain the used FAR over T or per one attempt e.g. CRC/sequence length in LP-WUS design.

Agreement

RAN1 further study the designs [target]/techniques of LP-WUS to have a comparable coverage as NR channel X. The NR channel X is

• Option #1: PDCCH for paging
• Option #2: PUSCH for message3
• FFS other options, e.g., between option1and option2 (better than PUSCH, worse than PDCCH)
• The final design will jointly consider the coverage with other KPIs
• FFS additional detail assumptions for NR channels, e.g., the message size for MSG3 and etc.

Agreement

Confirm Alt 2 in the following agreement and update as follows

Agreement

For evaluation, at least for FR1 MR ultra-deep sleep state, (Ramp-up and down transition energy, ramp-up time) is as follows,

·          Alt 1: (15000, 400ms) as baseline

·          Alt 2: ([40000], [800ms])

Company to report which alternative they use for which use cases.

For the remaining details on the evaluations aspect for LP-WUS, the email discussions are extended until April 28th 9AM UTC.

Decision: As per email decision posted on April 28th,

Agreement

Confirm the WA from RAN1#112 and update as followings

Working Assumption

·        For evaluation of LP-WUR frequency and time errors, the following is used,

·        Company to report how to use the clocks for LR on/off states

o   The above clock assumptions for LR assumes the MR is in ‘ultra-deep sleep’ power state.

o   For Option 3/4,

§  FFS applicability when MR is in ultra-deep sleep power consumption state and associated power consumption for LR on state and LR off state,

·        e.g., option 3/4 is not applicable

o   when MR is in ‘ultra-deep sleep state’ with [0.015] power units and LR is in off state or,

o   when LR monitoring power less than [TBD] power unit,

o   Note: Assumptions important for achieving performance by option 1/2/3/4 clock for LR should be declared, including active on/off power, transition energy/ ramp-up time T_{LR, ramp-up} for LR and etc.

o   If MR is in other state than ‘ultra-deep sleep state’, the clock running for MR can be used for LR.

§  assumptions important for achieving performance by using MR clock for LR should be declared

o   Other clock accuracy options are not precluded. Companies to report options based on a feasibility analysis of clock power consumption and UE power consumption to use the clock accuracy option

·        Company to report the frequency error assumption for the detection of LP-WUS/synchronization signal,

o   The following are examples for consideration, other approaches are not precluded,

§  Model 1:

·        The relationship between a drifted frequency error(ΔF), frequency drift ( F’) over a time (T1) is ΔF = ±F’ * T1

·        When frequency displacement [Fd] reaches max frequency error, it is assumed to be equaled to max frequency error

·        T1 is the time from the previous frequency synchronization. T1 may take different values depending on the chosen frequency synchronization approach.

·        FFS: Frequency displacement (Fd), defined as the difference between ideal frequency and frequency due to 1) clock drifting (ΔF); and 2) residual frequency error from previous synchronization/calibration (Fr), is given as Fd (ppm)=ΔF (ppm) +Fr(ppm).

§  Model 2: random frequency drifting, FFS details

·        Company to report the timing drifting error assumption for the detection of LP-WUS/synchronization signal,

o   The following are examples for consideration, other approaches are not precluded,

§  Model 1 [R1-2301438] [R1-2301558][R1-1714993]:

·        The relationship between the maximum frequency error(F_e) and corresponding timing drift( ΔT) over a time(T) is ΔT = ±F_e * T (linear region)

·        The relationship between a frequency drift( F’), and corresponding timing drift(ΔT) over a time(T) is ΔT = Fr*T ±0.5 * F’ *T² (transient region)

·        The transition between transient and linear region (from synchronization or calibration point/time) occurs at time [Ts= (Fe-Fr)/( F’)]

·        T is the time from the previous time synchronization. T may take different values depending on the chosen synchronization approach

·        FFS: Time error (Te) before detection of a current sync signal is defined as the difference between ideal time of the current sync signal and the time error due to 1) clock time drift (ΔT); and 2) residual time error from previous synchronization/calibration (Tr); Te= ΔT+ Tr

·        Model 2: random time drifting, FFS details

·        FFS: Phase noise model

Working Assumption

The following for usage of the clock is assumed for LP-WUR OFF/ON

[Note1: Any additional LO/FLL/PLL could start running during LP-WUR On duration. The power consumption of any of those LO/FLL/PLL is captured in LP-WUR On power]

FFS: Note2: option 3/4 can only be assumed when LP-WUR ON power value and LP-WUR OFF power value>=TBD2, option 1/2 can only be assumed when LP-WUR ON power value and LP-WUR OFF power value>=TBD1

Note3: The clock error (of both RTC and LO) could be improved to be less than max ppm error of option 1,2,3,4 with clock calibation based on sync signal such as LP-SS or preamble.

Final summary in R1-2304287.

R1-2304151         FL summary #1 of evaluation results on LP-WUS/WUR          Moderator (vivo)

Document for information only.

9.11.2     Low power WUS receiver architectures

R1-2302340         Discussion on architecture of LP-WUS receiver          Huawei, HiSilicon

R1-2302391         Discussion on low power wake up receiver architectures          Panasonic

R1-2302507         Discussion on low power wake-up receiver architecture           vivo

R1-2302571         Discussion on low power WUS receiver       OPPO

R1-2302688         Low-Power WUS receiver Architectures and its performance  CATT

R1-2302816         Discussion on LP-WUS receiver architecture              Intel Corporation

R1-2302828         Discussion on LP-WUS receiver architectures            InterDigital, Inc.

R1-2302891         Low Power WUS receiver architectures        Nokia, Nokia Shanghai Bell

R1-2302949         LP-WUS receiver architectures       ZTE, Sanechips

R1-2303151         Receiver architecture for LP-WUS  Samsung

R1-2303333         Low power WUS receiver architectures        MediaTek Inc.

R1-2303506         On low power wake-up receiver architectures             Apple

R1-2303613         Receiver architecture for LP-WUS  Qualcomm Incorporated

R1-2303729         Discussion on low power WUS receiver architectures NTT DOCOMO, INC.

R1-2303760         Low power WUS receiver architectures        Ericsson

[112bis-e-R18-LP_WUS-02] – Sigen (Apple)

Email discussion on LP WUS receiver architecture by April 26th

-        Check points: April 21, April 26

R1-2303941        Summary #1 on LP WUR architectures    Moderator (Apple)

From April 18th GTW session

Agreement

Provide the following response to RAN4 on “Whether IoT/wearables/smartphone UE types are all considered for LP-WUR design”:

·        Yes, IoT/wearables/smartphone UE types are all considered for LP-WUR design, according to the following agreement made in RAN1#112:

Agreement

Provide the following response to RAN4 on “Whether FR1 is considered as first priority frequency range”:

·        Yes, FR1 is considered as first priority frequency range in RAN1, and it is still FFS whether FR2 should be included in the scope of the SI.

Agreement

Provide the following response to RAN4 on “Whether in-band power boosting of LP-WUS is considered from RAN1 perspective”:

·        RAN1 is considering as part of evaluation, the in-band power boosting of LP-WUS. As the starting point for link level simulations for LP-WUS, RAN1 has agreed on the following for the modelling of adjacent subcarrier interference. RAN1 would appreciate feedback from RAN4, if any, on the power boosting assumptions made in RAN1.

Agreement

OOK-2 can be received using the agreed receiver architectures for OOK with parallel envelope detection.

Decision: As per email decision posted on April 21st,

Agreement

Provide the following response to RAN4 on “Power consumption, coverage and SNR targets”:

·        RAN1 has not reached any agreements on LP-WUR power consumption targets. RAN1 is still studying it.

o   For the power consumption of LP-WUR, the following power model was agreed for evaluation purpose. Note that the power consumption is defined as the relative power w.r.t. the deep sleep state of the main radio following the non-RedCap UE power model defined in Section 8.1 of TR 38.840. The UE power model for RedCap UEs can be found in Section 6.2 of TR 38.875.

·        RAN1 has not reached any agreements on the coverage and SNR targets for LP-WUR. RAN1 is still studying these aspects.

o   For evaluation of the coverage of LP-WUS, RAN1 has agreed to use MIL as the metric, with more details in the following agreement.

Agreement

Provide the following response to RAN4 on “Max occupied RB number in channel bandwidth for LP-WUS, for 1.4MHz and 5MHz RF bandwidth case”:

·        For the bandwidth of LP-WUS, RAN1 has agreed on the following:

·        RAN1 has not discussed the RF bandwidth of 1.4MHz for LP-WUS, and has not reached any conclusion on the maximum occupied RB number in 5MHz RF bandwidth case for LP-WUS. As the starting point for link-level simulations of LP-WUS, RAN1 has agreed on the following for LP-WUS bandwidth, the guard band and the filter.

Agreement

Provide the following response to RAN4 on “Possible supported SCS for LP-WUS, if applicable”:

·        RAN1 has reached the following agreement on SCS:

• In addition, as the starting point for link level simulations for LP-WUS, RAN1 has agreed on the following assumptions for LP-WUS:

R1-2303942        Summary #2 on LP WUR architectures    Moderator (Apple)

From April 24th GTW session

Agreement

Provide the following response to RAN4 on “Whether WUS can be located in a band separate from the UE’s NR band”:

·        RAN1 has reached the following agreement, and the case where WUS is located in a band separate from the UE’s NR band is to be further studied from RAN1 perspective.

R1-2303943        Summary #3 on LP WUR architectures    Moderator (Apple)

From April 26th GTW session

Agreement

Observation for FSK with frequency to amplitude conversion:

• The FSK architectures with frequency to amplitude conversion is applicable to single-SC FSK, but it may be challenging to make the frequency to amplitude conversion work well with multi-subcarrier FSK.
• Note: single-SC FSK refers to the waveform where each frequency segment has a single subcarrier, and multi-subcarrier FSK refers to the waveform where each frequency segment has multiple subcarriers, as described in the agreements for FSK-1 and FSK-2.

Email discussion is extended until April 28th 9AM UTC

R1-2304250        [Draft] Reply LS to RAN4 on LP WUR architectures          Moderator (Apple)

Decision: As per email decision posted on April 28th, the draft LS is revised and endorsed as R1-2304288. Final LS is approved in R1-2304251.

Final summary in R1-2304249 ( including a spreadsheet "R1-2304249 LP WUR architecture analysis results_template_v001" that can be used to collect the architecture analysis for the next meeting).

9.11.33     L1 signal design and procedure for low power WUS

Including any higher layer protocol changes relevant to RAN1.

R1-2302332         LP-WUS Physical Signal Design    FUTUREWEI

R1-2302341         Signal design and procedure for LP-WUS     Huawei, HiSilicon

R1-2303894         Discussion on low power wake up signal design         Panasonic            (rev of R1-2302392)

R1-2302409         L1 signal design and procedure for low power WUS  TCL Communication Ltd.

R1-2302508         Discussion on physical signal and procedure for low power WUS          vivo

R1-2302572         Design consideration on lower power wake-up signal and procedure      OPPO

R1-2302622         Discussion on L1 signal design and procedure for low power WUS        Spreadtrum Communications

R1-2302689         Physical layer signals/procedures and higher layer protocol for Low-Power WUR               CATT

R1-2302817         Discussions on L1 signal design and procedure for LP-WUS    Intel Corporation

R1-2302829         Discussion on L1 signal design and procedure for LP-WUS     InterDigital, Inc.

R1-2302862         On L1 signal design and procedures for low power WUS          Sony

R1-2302892         L1 signal design and procedures for low power WUS Nokia, Nokia Shanghai Bell

R1-2302950         LP-WUS design and related procedure          ZTE, Sanechips

R1-2302969         Discussions on L1 signal design and procedure for low power WUS      xiaomi

R1-2303900         Discussion on signal design and procedure for LP-WUS           China Telecom    (rev of R1-2303033)

R1-2303061         L1 signal design and procedure for low-power WUS  Sharp

R1-2303152         Signal design and procedure for LP-WUS     Samsung

R1-2303255         Discussion on L1 signal design and procedure for LP-WUS     CMCC

R1-2303334         L1 signal design and procedure for low power WUS  MediaTek Inc.

R1-2303421         Discussion on L1 signal design and procedure for low power WUS        EURECOM

R1-2303430         Discussion on L1 signal design and procedure for LP-WUS     LG Electronics

R1-2303507         On the L1 signal design and procedures for low power wake-up signal  Apple

R1-2303538         On LP-WUS signal design Nordic Semiconductor ASA

R1-2303614         L1 signal design and procedures for LP-WUR             Qualcomm Incorporated

R1-2303673         Discussion on L1 signal design and procedure for LP-WUS     NEC

R1-2303730         Discussion on L1 signal design and procedure for low power WUS        NTT DOCOMO, INC.

R1-2303761         L1 signal design and procedure for low power WUS  Ericsson

R1-2303808         Discussion on the L1 signal design and procedure for low power WUS  Lenovo

[112bis-e-R18-LP_WUS-03] – Karol (Nordic Semiconductor)

Email discussion on L1 signal design and procedure for low power WUS by April 26th

-        Check points: April 21, April 26

R1-2304036        Summary#1 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

Presented in April 18th GTW session.

R1-2304095        Summary#2 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From April 20th GTW session

Agreement

• Capture in TR: From RAN1 perspective, LP-WUS and signals/channels used by MR can be within the same FR1 band.
• At least LP-WUS and signals/channels by MR can be on the same carrier in the band
• Study further
• Whether LP-WUS and signals/channels used by MR can be different carriers in the band
• Details on the LP-WUS location within a carrier
• Whether LP-WUS is applicable for TDD / FDD (with full duplex operation)
• Band can be different than band of signals/channels used by MR
• LP-WUS association with BWP
• LP-WUS can be configurable within guard-band of a band (like NB-IoT)

R1-2304144        Summary#3 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From April 24th GTW session

Agreement

Update the RAN1#112 agreement as the following:

• [time/frequency resources (including any guard bands), if applicable]
• [total energy of LP-WUS across the time/frequency resources]

For Working assumption in place of the above deleted bullets:

• Alt 1:
• average EPRE within the [time]/frequency resources used for LP-WUS (including any guard bands)
• time/frequency resources used for LP-WUS (including any guard bands)
• Alt 2:
• average EPRE within the [time]/frequency resources used for LP-WUS (including any guard bands)
• SNR is calculated as average EPRE divided by power of noise [and interference].
• Companies to report whether and how power pooling across and within MR OFDMA symbols is used.
• FFS: PAPR applicable to LP-WUS

Agreement

Replace in RAN1#112 agreement

Companies to report

• power consumption of the MR if false alarm probability/rate not fixed across MC-ASK, MC-FSK, and CP-OFDMA waveforms

with

• receiver architecture type and its relative power consumption

Agreement

• For IDLE/INACTIVE mode study at least following candidates for content of LP-WUS
• information on which user(s) is/are targeted by the LP-WUS
• e.g. UE-group, -subgroup or -ID
• FFS: cell information
• FFS: SI change and ETWS/CMAS information, tracking area information, and RAN area information
• For CONNECTED mode, study at least following candidates for content of LP-WUS
• information on which user(s) is/are targeted by the LP-WUS
• e.g UE-group, -subgroup or -ID
• indication to wake-up to PDCCH monitoring.
• Other information candidates are not precluded
• Study pros and cons of including above information to LP-WUS.
• Note: the information may be explicitly or implicitly indicated.

Agreement

• For RRC connected mode, the following is assumed for LP-WUS study in RAN1
• RLM/BFD/CSI are performed by UE Main Radio (MR)
• RRM measurements are performed by UE Main Radio (MR)
• Ultra-deep sleep state is not allowed for MR.
• Study additional support of RRM measurement by LP-WUR for RRC connected mode
• Study RRC connected mode LP-WUS functionality/purpose/procedures
• Study RRC connected mode LP-WUS activation/deactivation procedures.
• Study RRC connected mode LP-WUS BW, whether same as IDLE/Inactive mode or different
• In RRC connected, study the relationship between LP-WUS and legacy UE power saving techniques.

R1-2304248        Summary#4 of discussions on L1 signal design and procedure for low power WUS      Moderator (Nordic Semiconductor ASA)

From April 26th GTW session

Agreement

• Study further following alternatives to carry the LP-WUS information using:
• Alt 1: by sequence(s) detection/selection 
• FFS sequence type
• Alt 2: by encoded bits
• FFS: what type of encoding scheme
• FFS: with or without other bits (e.g. CRC/FCS)
• Other alternatives are not precluded
• Study whether LP-WUS information needs to be preceded by known one or more sequence(s).

Agreement

At least for IDLE/Inactive mode, at least one BW-size <=5MHz is recommended to be supported for FR1

• Other BW sizes are not precluded
• if additional BW-size(s) are recommended to be supported, BW-size can be up to 20MHz
• LP-WUS bandwidth size (including guard-bands) is assumed to be an integer number of PRBs

Agreement

Study further methods to modulate input signal of the DFT/Least-Square block for OOK-4, and methods to modulate input signal of N SCs for other MC-ASK/FSK schemes

• study methods with respect to
• improving frequency diversity by flattening the spectrum, frequency repetition and frequency hopping
• impact to dynamic range of RE power in frequency domain
• FFS: impact to PAPR of generated time domain modulated MC-ASK/FSK symbol
• improving robustness to timing error necessary spectrum adjustment for compatibility with CP-OFDM generation

Agreement

• Study techniques/mechanisms to enhance coverage performance of LP-WUS
• Study potential gains available as well as drawback(s) of the technique(s)/mechanisms(s), e.g. system overhead, increased complexity network energy consumption etc…
• Study potential issues and corresponding solutions for the case when LP-WUS coverage is insufficient
• At least study fallback mechanisms where the Main Radio switches to legacy operation in case the channel condition of LP-WUS is not sufficient, e.g. below threshold.

R1-2304269         Collection of LLS results on low power WUS             Moderator (Nordic Semiconductor ASA)

Document is for information. Companies can use it for calibration of the next round of results.